Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1259

reference
491-tree-1
name
1259
tree-preservation-order

undefined

491-tpo-1
uprn
address-text
point
POINT (-1.023267 50.883139)
geometry
MULTIPOLYGON (((-1.023196 50.883132,-1.023199 50.883146,-1.023209 50.883158,-1.023225 50.883168,-1.023244 50.883175,-1.023266 50.883177,-1.023288 50.883175,-1.023308 50.883169,-1.023324 50.883159,-1.023334 50.883147,-1.023338 50.883133,-1.023335 50.883119,-1.023325 50.883106,-1.023310 50.883096,-1.023290 50.883090,-1.023268 50.883087,-1.023246 50.883089,-1.023226 50.883095,-1.023210 50.883105,-1.023200 50.883118,-1.023196 50.883132)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL